Troubleshooting Solr

When starting Solr, error message contains “Address already in use: bind”

This error means Solr cannot access the configured network address.

Possible Causes

• Another process (perhaps an existing Solr instance) is already using the network address.
• Java does not have access to the network

To determine if another process is using the address, you can run the netstat command with -o parameters in Command Prompt to check the ports and the PID tied up to the port. Then based on the PID, run the tasklist command or use the task manager to find out which program/service is occupying the port using the port. Alternatively, you can use the third party tool TCPView to check the program/service occupying the specific port.

To ensure Java is configured to access the network, you can use check the network settings in the Java Control Panel.

When starting Solr, error message contains “JAVA_HOME”

This error means Solr cannot find Java because the JAVA_HOME system variable is not set.

You can use the Environment Variables window available from the System Properties control panel to create the JAVA_HOME environment variable. Make sure to create the variable as a system variable, not a user variable. Remember that it may be necessary to restart the server or command prompt to make the new variable settings active.

The full data import does not complete within a few minutes

The full data import should complete within a few minutes and the Logging page indicates Solr cannot connect to the database server.

Possible Causes

• The connection information specified in db-data-config.xml is not correct
• Solr does not have network access to the SQL Server

To verify the connection information, edit db-data-config.xml in the kommerceserver core directory as described in Updating the db-data-config File.

You can connect using SQL Server Management Studio from the Solr server to verify the settings. It may be necessary to enable TCP/IP protocol.